Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix two issues relating to a bug that caused runners not to exit #37

Merged
merged 1 commit into from
Jan 8, 2024

Conversation

benjaminwood
Copy link
Contributor

A NoMethodError was being raised when we called runner.finish in the handle_close method of the controller. This was preventing the runner from exiting, and it wasn't clear why because the rescue was swallowing the error.

Our intent is to rescue no method errors when there is no handler defined for a provided command. The new approach is to use respond_to to determine this vs rescuing all NoMethodErrors.

A NoMethodError was being raised when we called `runner.finish` in the
`handle_close` method of the controller. This was preventing the runner
from exiting, and it wasn't clear why because the rescue was swallowing
the error.

Our intent is to rescue no method errors when there is no handler
defined for a provided command. The new approach is to use respond_to
to determine this vs rescuing all NoMethodErrors.

Co-authored-by: Nate Vick <nate.vick@hint.io>
@benjaminwood benjaminwood self-assigned this Jan 8, 2024
@benjaminwood benjaminwood merged commit 8ca7029 into main Jan 8, 2024
4 checks passed
@benjaminwood benjaminwood deleted the fix-bugs-preventing-runner-exit branch January 8, 2024 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants